docs: add AEO cross-links for agents and orchestration#265
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds three targeted internal links that connect agent overview and deployment-pattern content to the canonical Scheduled Agents, multi-agent orchestration, and integrations pages. The linked destinations exist in the docs tree, the changes are scoped to existing AEO/source-data rationale, and the diff does not introduce code or configuration security concerns.
Concerns
- No blocking concerns found.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
Closing this out — the docs were restructured in #262 (merged 2026-06-30), which moved
Rather than hand-rebase a small, auto-generated cross-link PR, I'm closing it. The Resolved as part of an Oz-assisted review of the AEO cross-link workflow. |
* docs(skills): make aeo_crosslink_audit reliable + set biweekly cadence Assessment of the scheduled AEO cross-link agent found the run log has never populated and several noise sources in the automated PRs. Fixes: - Run logging: never commit to protected main (direct commits failed silently, leaving the log empty and blocking improve-aeo-crosslink-skill). Use a standing chore/aeo-crosslink-audit-log branch + one perpetual PR. - Dedup/supersede: check for an existing open cross-link PR before opening; never leave two open at once (prevents duplicates like #232 vs #228). - Low-signal runs: prefer a no-change report over weak docs-only PRs when neither Peec nor GSC signals are usable. - Restructure-safety: re-validate edited files and link targets against the latest main and resolve redirects before opening (prevents #262/#265-style breakage where cloud-agents moved to platform/). - Document biweekly cadence. - improve-skill: note the standing log PR must be merged before analysis. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(skills): align documented biweekly cron with live 15:00 UTC run time Co-Authored-By: Oz <oz-agent@warp.dev> * docs(skills): drop biweekly Schedule section; keep weekly cadence Co-Authored-By: Oz <oz-agent@warp.dev> * Update .agents/skills/aeo_crosslink_audit/SKILL.md Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> --------- Co-authored-by: Oz <oz-agent@warp.dev> Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
AEO cross-link audit
Small, high-confidence internal cross-links for agents, cloud agents, and orchestration docs, sourced from the Peec AEO snapshot (
buzz/aeo-snapshots/docs/agents-orchestration/latest.json, generated 2026-06-24).Goal
Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs so readers can jump from an overview/concept page to the canonical page for the workflow they're researching.
Source signals
Top Peec prompt clusters this period (all high or medium volume):
Pages touched
src/content/docs/agent-platform/getting-started/agents-in-warp.mdx— the "From local to cloud" section names scheduling and parallel execution but only linked to the cloud agents overview.src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx— the "Common ways to trigger" list named first-party integrations (Slack, Linear) without linking to the integrations docs.Links added
agents-in-warp.mdx→ Scheduled Agents — anchored on "schedules" in the "Run on schedules for recurring tasks" bullet. Backed by the high-volume scheduling prompt cluster.agents-in-warp.mdx→ Multi-agent orchestration — anchored on "in parallel across repos or tasks". Backed by the parallel/multi-agent prompt clusters.deployment-patterns.mdx→ Integrations overview — appended to the "First-party integrations (Slack, Linear, etc.)" trigger bullet. Backed by the Slack/Linear/GitHub trigger prompt cluster.Reader next step
Open questions for human review
deployment-patterns.mdxinstead to keepagents-in-warp.mdxto two new links; reviewers may prefer also linking integrations directly on that bullet.Follow-up recommendations (out of scope for this cross-link pilot)
Conversation: https://app.warp.dev/conversation/1605300e-6a83-496f-9ccd-32d244d6df5d
Run: https://oz.warp.dev/runs/019f13e4-fb3c-7d09-843f-46e4742674de
This PR was generated with Oz.